-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sdfw_services: psa_crypto: use new tags for pointer-to-const members #19808
sdfw_services: psa_crypto: use new tags for pointer-to-const members #19808
Conversation
CI InformationTo view the history of this post, clich the 'edited' button above Inputs:Sources:sdk-nrf: PR head: a36dee5ae161f042d8efd9c96c847ea3982adad6 more detailssdk-nrf:
Github labels
List of changed files detected by CI (26)
Outputs:ToolchainVersion: 11349092be Test Spec & Results: ✅ Success; ❌ Failure; 🟠 Queued; 🟡 Progress; ◻️ Skipped;
|
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publish GitHub Action. |
baa7f3e
to
dfb802b
Compare
The following west manifest projects have changed revision in this Pull Request:
✅ All manifest checks OK Note: This message is automatically posted and updated by the Manifest GitHub Action. |
dfb802b
to
493459f
Compare
Regenerate code using the current zcbor version. Signed-off-by: Jonathan Nilsen <[email protected]>
This lets the server loosen the required permissions when validating pointers-to-const parameters so that only read permissions are required for these. Note that this CDDL update is not backwards compatible, and the service version is bumped to 2. Ref: NCSDK-31182 Signed-off-by: Jonathan Nilsen <[email protected]>
493459f
to
a36dee5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Flip the order of these commits, the changes to the source files should be before the re-generation of files using said source files, otherwise the history makes no sense
Sorry if the commits/description were unclear on this, but the first commit is re-generating the code without any changes to the source files but using the latest zcbor version that is checked out by the manifest (partial duplicate of #16974). Then the second commit changes one of the source files and re-generates code based on that file in the same commit. I split it to try keeping the irrelevant diff in the first commit, but I can merge the two commits if you prefer. |
Fine to keep it as 2 commits since it's 2 operations not the 1 I assumed |
Relevant changes are in the second commit.
The first commit is just regenerating zcbor code.